-
Notifications
You must be signed in to change notification settings - Fork 47.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Revert "feat: honor displayName of context types" #18223
Conversation
This reverts commit 45c172d.
This pull request is automatically built and testable in CodeSandbox. To see build info of the built libraries, click here or the icon next to each commit SHA. Latest deployment of this branch, based on commit a4f6cfe:
|
Details of bundled changes.Comparing: 6a0efdd...a4f6cfe react
React: size: 0.0%, gzip: 0.0% Size changes (experimental) |
Details of bundled changes.Comparing: 6a0efdd...a4f6cfe react
React: size: 0.0%, gzip: 0.0% Size changes (stable) |
@trueadm Could you share what you're doing internally so that we can get this in properly? |
You mean you're setting the |
Even if it's unsupported, this is a breaking change if not fixed. :-) |
Sure I can go ahead and add a warning to the setter. I just think this stance locks any object shape once released because someone might set unsupported properties. I just need to know what the expected behavior should be. |
Sorry, I meant the context consumer object. |
)" (facebook#18223)" This reverts commit 3ee812e.
Reverts #18035. This breaks an internal FB test where we try and set the
displayName
on the context consumer. Otherwise we get this runtime exception:TypeError: Cannot set property displayName of #<Object> which has only a getter